Skip to content

Fix outdated links#4506

Open
beckykd wants to merge 10 commits intomainfrom
bd-update-external-links
Open

Fix outdated links#4506
beckykd wants to merge 10 commits intomainfrom
bd-update-external-links

Conversation

@beckykd
Copy link
Collaborator

@beckykd beckykd commented Jan 9, 2026

Related to #4336

@review-notebook-app
Copy link

Check out this pull request on  ReviewNB

See visual diffs & provide feedback on Jupyter Notebooks.


Powered by ReviewNB

@qiskit-bot
Copy link
Contributor

One or more of the following people are relevant to this code:

Copy link
Member

@frankharkins frankharkins left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you!

For the links in the API docs, we'll need to add the redirects to scripts/config/external-redirects.ts, otherwise these changes will be discarded when we next regenerate the docs from source.

The format is:

"old":
  "new",

E.g.

"https://aip.scitation.org/doi/10.1063/1.5141835":
"https://pubs.aip.org/aip/jcp/article/152/12/124107/953761/Quantum-orbital-optimized-unitary-coupled-cluster",

@beckykd
Copy link
Collaborator Author

beckykd commented Jan 12, 2026

we'll need to add the redirects

Even though the changes will be made in the API docs themselves?

@frankharkins
Copy link
Member

frankharkins commented Jan 12, 2026

Even though the changes will be made in the API docs themselves?

Yep: We store the original API docs HTML in Box and sometimes re-run the HTML -> markdown pipeline to fix bugs. When this happens, your fixes will be overwritten by the pipeline with the original links. The external-redirects.ts tells the pipeline to do the same link substitution that you've done in this PR.

@beckykd beckykd mentioned this pull request Jan 12, 2026
@beckykd
Copy link
Collaborator Author

beckykd commented Jan 15, 2026

@frankharkins what should we do about links that are broken in historical API documents but don't exist in more recent documents? For example, qaiskit-ibm-runtime/0.40/qiskit-runtime-service links to https://auth.quantum.ibm.com/api. That API no longer exists and the link was just deleted from the later versions.

Copy link
Collaborator

@arnaucasau arnaucasau left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for working on this, Becky!!

* The `channel_strategy` parameter in `QiskitRuntimeService` has been removed. To continue using Q-CTRL in your workflow, please explore the following options:

> * If your organization has an existing IBM Quantum Premium Plan instance: migrate to the Q-CTRL Performance Management Function, found in the [Qiskit Functions Catalog](https://quantum.ibm.com/functions).
> * To continue using Qiskit Runtime with IBM Cloud: migrate to Q-CTRL Fire Opal, the same performance management product accessible directly through Q-CTRL. You can [connect your IBM Cloud API key and Qiskit Runtime CRN](https://docs.q-ctrl.com/fire-opal/discover/hardware-providers/how-to-authenticate-with-ibm-credentials) to Fire Opal. ([1966](https://github.com/Qiskit/qiskit-ibm-runtime/pull/1966))
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This link needs to be fixed in the runtime repo

Jessie said to just ignore it, since it's in a really old release note. I'll add to the Ignore file.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Unfortunately, we can't ignore the issue because it's in the release notes. Our script regenerates the whole release note file with each version, so we would revert the change in the future if it's not fixed.

We can only ignore issues with historical versions if it's in a page different than the release notes :(

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In my opinion we should fix it on the runtime repo and remove the redirect in external-redirects.ts given that it won't be necessary anymore

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OK

@frankharkins
Copy link
Member

@frankharkins what should we do about links that are broken in historical API documents but don't exist in more recent documents? For example, qaiskit-ibm-runtime/0.40/qiskit-runtime-service links to https://auth.quantum.ibm.com/api. That API no longer exists and the link was just deleted from the later versions.

I think if a link has no replacement, it's OK for it to be broken in a historical version. These are archives after all and it might even be helpful for a user to know that the API isn't available any more.

Maybe just update the comment to explain we're not going to fix them.

@beckykd
Copy link
Collaborator Author

beckykd commented Feb 3, 2026

These are the changes being made in the API file:

I updated the comment in the Ignore.ts file to explain why we're leaving the links that don't have a replacement as-is in the old API docs. I also added the redirects listed to the external-redirects file.

Comment on lines 46 to 47
"https://docs.q-ctrl.com/fire-opal/discover/hardware-providers/how-to-authenticate-with-ibm-credentials":
"https://docs.q-ctrl.com/fire-opal/discover/hardware-providers/how-to-migrate-from-performance-management-on-ibm-cloud",
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

// but they will never be fixed in the old API docs. We decided to leave these links as-is for archival purposes.
"https://github.com/Qiskit/ibm-quantum-schemas/blob/main/schemas/backend_status_schema.json",
"https://github.com/Qiskit/ibm-quantum-schemas/blob/main/schemas/default_pulse_configuration_schema.json",
"https://docs.q-ctrl.com/fire-opal/discover/hardware-providers/how-to-authenticate-with-ibm-credentials",
Copy link
Collaborator

@arnaucasau arnaucasau Feb 4, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we need this link to be ignored now? I think we can remove it if it only appears in the qiskit-ibm-runtime release notes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: No status

Development

Successfully merging this pull request may close these issues.

4 participants